Hi (again)Things seem to have been going largely well in the implementation of Exchange 2007, apart from a couple of niggles. This being the latest one. Basically, we get a message saying the default hub transport installation is corrupted because we're using the default properties.I've gone in to change a couple of items, namely on the network tab under 'use these local IP addresses to receive mail' and 'receive mail from remote servers that have these ip addresses'.Under 'use these local ipaddresses to receiv mail', I select 'all available which defaults to port 587.Under 'receive mail from remote servers that have these ip addresses', I select our spam filter with an ip address of 195.106.2.202/24 - I have also tried just the ip address on its own with no mask bits.When I hit OK through the EMC, I get this message:'Failed to convert 0000:0000:0000:0000:0000:0000:0.0.0.0-ffff:ffff:ffff:ffff:ffff:ffff:255.255.255.255 from System.String to Microsoft.Exchange.Data.IPRange'Which doesn't make sense, as I am trying to change the defaults (which have been removed at this point.I then tried from the EMS to see if it gave me any more information and got this:[PS] C:\xxxxxx\xxxxxx>add-ipallowlistentry -ipaddress 195.106.2.202/24Add-IPAllowListEntry : Cannot bind parameter 'IPAddress'. Cannot convert value "195.106.2.202/24" to type "System.Net.IPAddress". Error: "An invalid IP address was specified."At line:1 char:32[PS] C:\xxxx\xxxxx>add-ipallowlistentry -ipaddress 195.106.2.202 Identity IPRange ExpirationTime HasExpir ed-------- ------- -------------- --------1 195.106.2.202 31/12/9999 23:59:59 False+ add-ipallowlistentry -ipaddress <<<< 195.106.2.202/24Thinking it was done, I then went back to the EMC to see if it had updated, but it hasn't and I still get the error messages?!?!ANy suggestions?Thanks

Can you please let us know where are you getting message saying default hub transport installation is corrupted and also post exact error message? Client <ServerName> Receive connector is used toaccepts SMTP connections from all non-MAPI clients, such as POP and IMAP. Now if you set the limited ip range here then POP and IMAP clients won't be able to relay emails through Exchange server and that is permissioned for Exchange Users only so you don't have to worry about spam. Receive Connector Properties > Network Tab http://technet.microsoft.com/en-us/library/aa998876.aspx Configuring Hub Transport Server Connectors http://technet.microsoft.com/en-us/library/aa995965.aspx Add-IPAllowListEntry cmdlet is to add an IP address or IP address range to the IP Allow list configuration information for the Connection Filter agent and nothing related to Receive Connectors. To modify Receive Connector RemoteIPRange entry you can use Set-ReceiveConnector cmdlet withRemoteIPRanges parameter. Set-ReceiveConnector http://technet.microsoft.com/en-us/library/bb125140.aspx Amit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com

HiWhen I open the EMC, I go to server configuration->Hub transport. I have the name of the transport server on the top and two receive connectors below called:clienthubdefaulthubIt doesn't matter which of these I click, I get the following message as soon as I have double clicked it:The proprties on client/default hub have invalid data. If you click 'OK' default values will be used instead and will be saved if you do not change them before hitting apply or OK on the property page. If you click cancel the object will be displayed read-only and corrupted values will be retained.The following values have invalid data:RemoteIPRanges,Bindings.Thanks

This is the message I get when I open the EMC: get-receiveconnector warning:object x64hub\defaultx64exhub has been corrupted and is an inconsistent state. The following validation errors have been encountered: Warning:Could not convert property remoteiprange to typr iprange. The start and end ip addresses must be of the same family Warning:Binding addresses cannot be a multicast or a broadcast address or belong to an IPv6 family. warning:object x64hub\clientx64exhub has been corrupted and is an inconsistent state. The following validation errors have been encountered: Warning:Could not convert property remoteiprange to typr iprange. The start and end ip addresses must be of the same family Warning:Binding addresses cannot be a multicast or a broadcast address or belong to an IPv6 family.I have tried using the following command from the EMS:[PS] C:\Documents and Settings\xxxxxx>set-receiveconnector -identity:defaultx64hub -bindings:0.0.0.0:25Set-ReceiveConnector : The operation could not be performed because object 'defaultx64hub' could not be found on domain controller 'DC04.xxxxxx.com'.At line:1 char:21+ set-receiveconnector <<<< -identity:defaultx64hub -bindings:0.0.0.0:25I've tried different names and still get the same message - anything else to add?

Hi, IP Bindings: You must specify a local IPaddress that is valid for the Hub Transport server or Edge Transport server on which the Receive connector is located. If you specify an invalid local IPaddress, the Microsoft Exchange Transport service may fail to start when the service is restarted. To specify all IPaddresses that are configured on all network adapters, you can use the IPaddress 0.0.0.0. Because the uniqueness of a Receive connector is based on the IP Bindings (IP address and port) and the RemoteIPRanges, these values cannot be shared with other Receive connectors in the Organization. Furthermore, the RemoteIPRange cannot overlap if the Bindings (IP Address and Port) are identical between two or more connectors, with one exception. RemoteIPRanges defined on a connector can fall within the range of another connector even if the bindings are identical. For this issue please verify if the value on IP Bindings is in the RemoteIPRanges. Please try to use Get-receiveconnector |fl to check what value that you have specified for Bindings, RemoteIPRanges.Please post the output here. Regards, Xiu

Output below - thanks for your assistance[PS] H:\>get-receiveconnector |Fl AuthMechanism : Tls, Integrated, BasicAuth, BasicAuth RequireTLS, ExchangeServerBanner :BinaryMimeEnabled : TrueBindings : {0000:0000:0000:0000:0000:0000:0.0.0. 0:25, 0.0.0.0:25}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : FalseEnhancedStatusCodesEnabled : TrueFqdn : x64exhub.xxxxx.comComment :Enabled : TrueConnectionTimeout : 00:10:00ConnectionInactivityTimeout : 00:05:00MessageRateLimit : unlimitedMaxInboundConnection : 5000MaxInboundConnectionPerSource : unlimitedMaxInboundConnectionPercentagePerSource : 100MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 8MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 5000PermissionGroups : AnonymousUsers, ExchangeUsers, Exchan geServers, ExchangeLegacyServersPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : X64EXHUBSizeEnabled : EnabledWithoutValueTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Default X64EXHUBDistinguishedName : CN=Default X64EXHUB,CN=SMTP Receive C onnectors,CN=Protocols,CN=X64EXHUB,CN =Servers,CN=Exchange Administrative G roup (FYDIBOHF23SPDLT),CN=Administrat ive Groups,CN=NHS NWEST HN,CN=Microso ft Exchange,CN=Services,CN=Configurat ion,DC=xxxxxx,DC=comIdentity : X64EXHUB\Default X64EXHUBGuid : 2ba1c3c4-88de-46cd-a3a1-4911f7a8d0aeObjectCategory : xxxxx.com/Configuration/Schema/ms -Exch-Smtp-Receive-ConnectorObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 01/07/2009 15:11:18WhenCreated : 01/07/2009 11:52:55OriginatingServer : ns1.xxxxx.comIsValid : False WARNING: Object X64EXHUB\Default X64EXHUB has been corrupted and it is in aninconsistent state. The following validation errors have been encountered:WARNING: Could not convert property RemoteIPRanges to type IPRange. The startand end IP addresses must be of the same family.WARNING: Binding addresses cannot be a multicast or a broadcast address orbelong to an IPv6 address family.AuthMechanism : Tls, Integrated, BasicAuth, BasicAuth RequireTLSBanner :BinaryMimeEnabled : TrueBindings : {0000:0000:0000:0000:0000:0000:0.0.0. 0:587, 0.0.0.0:587}ChunkingEnabled : TrueDefaultDomain :DeliveryStatusNotificationEnabled : TrueEightBitMimeEnabled : TrueDomainSecureEnabled : FalseEnhancedStatusCodesEnabled : TrueFqdn : x64exhub.xxxxx.comComment :Enabled : TrueConnectionTimeout : 00:10:00ConnectionInactivityTimeout : 00:05:00MessageRateLimit : 600MaxInboundConnection : 5000MaxInboundConnectionPerSource : 20MaxInboundConnectionPercentagePerSource : 2MaxHeaderSize : 64KBMaxHopCount : 30MaxLocalHopCount : 8MaxLogonFailures : 3MaxMessageSize : 10MBMaxProtocolErrors : 5MaxRecipientsPerMessage : 200PermissionGroups : ExchangeUsersPipeliningEnabled : TrueProtocolLoggingLevel : NoneRemoteIPRanges : {0.0.0.0-255.255.255.255}RequireEHLODomain : FalseRequireTLS : FalseServer : X64EXHUBSizeEnabled : EnabledTarpitInterval : 00:00:05AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : Client X64EXHUBDistinguishedName : CN=Client X64EXHUB,CN=SMTP Receive Co nnectors,CN=Protocols,CN=X64EXHUB,CN= Servers,CN=Exchange Administrative Gr oup (FYDIBOHF23SPDLT),CN=Administrati ve Groups,CN=NHS NWEST HN,CN=Microsof t Exchange,CN=Services,CN=Configurati on,DC=xxxxx,DC=comIdentity : X64EXHUB\Client X64EXHUBGuid : 1eec5e70-ac6d-471b-8cc8-6f1b68d5849dObjectCategory : xxxxx.com/Configuration/Schema/ms -Exch-Smtp-Receive-ConnectorObjectClass : {top, msExchSmtpReceiveConnector}WhenChanged : 01/07/2009 11:53:26WhenCreated : 01/07/2009 11:52:56OriginatingServer : ns1.xxxxx.comIsValid : False WARNING: Object X64EXHUB\Client X64EXHUB has been corrupted and it is in aninconsistent state. The following validation errors have been encountered:WARNING: Could not convert property RemoteIPRanges to type IPRange. The startand end IP addresses must be of the same family.WARNING: Binding addresses cannot be a multicast or a broadcast address orbelong to an IPv6 address family.

Danny,I was creating a receive connector and was getting the not found on Domain Controller error myself. To resolve my issue i did the following:get-ReceiveConnector | Fl *identity*This will display the identity of your receive connectors. In my case it was "SERVER\Receive-Connector-Name" SO in your statement:set-receiveconnector -identity:defaultx64hub -bindings:0.0.0.0:25Try using this instead:set-receiveconnector"SERVER\receive-connector" -bindings:0.0.0.0:25Zach Smith